[CMSSW_14_0_X] Update L1T menu tag to L1Menu_Collisions2024_v1_2_0_xml #44861
Conversation
|
A new Pull Request was created by @perrotta for CMSSW_14_0_X. It involves the following packages:
@consuegs, @saumyaphor4252, @cmsbuild, @perrotta can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
cms-bot internal usage |
|
please test |
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-8fbe40/39129/summary.html Comparison SummarySummary:
|
|
+1
|
cmsbuild
added
alca-approved
fully-signed
and removed
alca-pending
pending-signatures
labels
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_14_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_1_X is complete. This pull request will now be reviewed by the release team before it's merged. @antoniovilela, @sextonkennedy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
|
+1 |
PR description:
Update L1T menu with L1Menu_Collisions2024_v1_2_0_xml, as from cmsTalk https://cms-talk.web.cern.ch/t/gt-mc-data-relval-update-of-the-2024-l1t-menu-tag-l1menu-collisions2024-v1-2-0/39826
The new L1T menu tag is
L1Menu_Collisions2024_v1_2_0_xmlwhich replaces the previousL1Menu_Collisions2024_v1_1_0_xml.The difference wrt the previous tag is just the addition of a few L1 HQ bits for lumi-decay.All the differences w.r.t. the previous L1T menu are summarized here , and can be visible also via the Payload Inspector:
GT differences with the previous ones only relate to the updated L1T menu tag:
PR validation:
See master branch.
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
backport of #44860